Proxy presence server

ABSTRACT

A method includes receiving, from an external presence server at a proxy presence device, a presence status request for presence information associated with a user device in a home carrier network. The method includes sending the presence status request to an internal presence server in the home carrier network. The method also includes receiving the presence status of the user device and storing the presence status of the user device with a time to live (TTL) in an associated database. The presence status is sent to the external presence server. The method includes receiving at least one subsequent request for the presence status of the user device within a time window of the TTL. The method also includes sending the presence status within the time window of the TTL without sending another presence status request to the internal presence server.

BACKGROUND

Presence servers may provide presence information regarding a potentialcommunication partner to subscribing user devices. Presence informationprovides a status indication of the ability and interest of thepotential communication partner to communicate with the subscribing userdevice. A subscribing user device (e.g., a user client) of the potentialcommunication partner may provide the presence information to a presenceservice, which may store this presence information in a personalavailability record (or presentity). The presence service may includeone or more presence servers.

The subscribing user device may include a Rich Communication Service(RCS) enabled address book that may periodically query the presenceservice for capability information relating to subscribers. For example,the subscribing user device may request information whether the listedsubscribers in the RCS enabled address book are high definition (HD)Voice enabled. In instances in which an RCS client (e.g., in thesubscribing user device) has determined that a subscriber has enhancedservices enabled, the RCS client will query the presence server again todetermine if the subscriber is currently in a network that supportsthose enhanced services when that contact is accessed. The RCS clientmay thereby prevent issuing an invite that requires particularcapabilities (e.g., an HD Voice invite) when the called party is roamingin coverage (e.g., 3G coverage) that does not support that particularcapability.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary network in which systems and methodsdescribed herein may be implemented;

FIG. 2 illustrates an exemplary configuration of one or more of thecomponents of FIG. 1;

FIG. 3 is a diagram of communications to determine presence informationassociated with a user device in a home network via the proxy presenceserver of FIG. 1;

FIG. 4 is a diagram of exemplary functional components of the proxypresence server of FIG. 1;

FIG. 5 depicts a functional block diagram of the external interfacemodule of FIG. 4;

FIG. 6 depicts a functional block diagram of the cache module of FIG. 4;

FIG. 7 depicts a functional block diagram of the query module of FIG. 4;and

FIG. 8 is a flowchart of an exemplary process for providing a proxypresence service for a user device associated with a home carriernetwork.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description isexemplary and explanatory only and is not restrictive of the invention,as claimed.

Systems and/or methods described herein may provide a proxy presenceservice for presence information associated with user devices in a homecarrier network via a proxy presence server. The proxy presence servermay act as an external interface for presence information to foreigncarriers via networking protocols (e.g., transmission controlprotocol/Internet protocol (TCP/IP), internetwork packet exchange (IPX),etc.).

Consistent with embodiments described herein, the systems may cachepresence information for subscribers for which the system has recentlyreceived queries for a predetermined amount of time. The cache may beconfigurable with a Time To Live (TTL). The systems and methods mayretrieve capabilities data for every subscriber on a configurableinterval. In instances in which another query is received for thatparticular subscriber, the query may be served directly from the proxypresence server, with no impact to an internal presence server. Theinternal presence server may receive, store, and transmit informationabout the presence or status of user devices associated with a homecarrier network.

As used herein, the terms “user,” “end user,” “subscriber,” and/or“customer” may be used interchangeably. Also, the terms “user,” “enduser,” “subscriber,” and/or “customer” are intended to be broadlyinterpreted to include a user device or a user of a user device.

FIG. 1 is a block diagram of an exemplary network 100 in which systemsand methods described herein may be implemented. Referring to FIG. 1,network 100 includes user devices 110-a through 110-x (referred tocollectively as user devices 110 and individually as user device 110),an internal presence server 120, a home carrier network 130, a proxypresence server 140, an external presence server 150, and an externalnetwork 170. The particular arrangement and number of components ofnetwork 100 shown in FIG. 1 are illustrated for simplicity. In practicethere may be more user devices 110, internal presence servers 120, proxypresence servers 140, external presence servers 150, and/or networks130/170. Additionally, network 100 may contain fewer components,different components, differently arranged components, or additionalcomponents than depicted in FIG. 1. For example, although not shown,network 100 may include network devices, session initiation protocol(SIP) proxy devices, and other devices that facilitate voice over longterm evolution (VOLTE) functions consistent with embodiments describedherein. Components of network 100 may be connected via wired and/orwireless links.

User device 110 may include any type of device that is able to transmitand receive data, such as text data, video data, image data, audio data,multi-media data, etc. For example, user devices 110 may include sometype of computer, such as a personal computer (PC), a tablet computer, alaptop computer, etc., a personal digital assistant (PDA), a web-basedappliance, a mobile terminal (e.g., a cellular telephone), etc. Userdevices 110 may also include a telephone, such as a public switchedtelephone network (PSTN) based telephone, an Internet-protocol (IP)based phone, a wireless telephone, etc., used to make and receivetelephone calls.

Furthermore, users of user devices 110 may be subscribers to telephonyservices provided in association with different carrier networks. Asshown in FIG. 1, user devices 110 may be associated with different homecarrier networks 130. For example, user devices 110 a-110 h may beassociated with the home carrier network 130. User devices 110 n-110 xmay be associated with external networks (or foreign networks) 170 tothe home carrier network 130 of user devices 110 a-110 c and 110 d-110f. Each of the user devices 110 may request presence informationassociated with subscribers listed in address books corresponding to theparticular user device 110. The address book may include listedsubscribers corresponding to user devices 110 associated with a homecarrier network 130 or a foreign network (to home carrier network 130).

User devices 110 may perform a poll that is triggered based on theconfiguration of the client of the particular user device 110. Eachvendor client may trigger a presence status poll of user devices 110 a-hassociated with home carrier network 130 with different criteria. Theuser device 110 may request presence information associated with eachentry whenever the input provided by a user triggers polling of theparticular entry. For example, some clients may poll each entry in theaddress book as a subscriber scrolls down their contact list on the userdevice 110. Other clients may only poll when the contact information fora particular entry is expanded to a detail level (e.g., prior toinitiating a call, etc.).

Internal presence server 120 may receive, store, and transmitinformation about the presence or status of user devices 110 associatedwith a home carrier network 130. For example, internal presence server120 may allow user devices 110 associated with a home carrier network130 to publish their status information (busy, available, etc.) so thatother user devices 110 may subscribe to the published presenceinformation. The presence information may be used for the video portionof a VOLTE call or other enhanced voice services that require presence.Presence information may include capabilities of a subscriber to makevideo calls, whether the user device 110 includes a camera, whether thecommunication is covered under a subscriber plan associated with theuser device 110, whether the user device 110 is currently in an LTEnetwork, etc. In some embodiments, internal presence server 120 mayimplement the Extensible Messaging and Presence Protocol (XMPP) topublish and subscribe to presence information. Alternatively, internalpresence server 120 may implement the Session Initiation Protocol (SIP)for Instant Messaging and Presence Leveraging Extensions (SIMPLE) forpublishing and subscribing to presence information.

Home carrier network 130 may refer to a communications network providedand operated by the home carrier company for particular user devices 110(e.g., user devices 110-a to 110-h). A carrier may refer to one or moreof a mobile network operator (MNO), a mobile phone operator, a carrierservice provider (CSP), a wireless service provider, a wireless carrier,a cellular company, and/or any other company that provides mobile phoneservice(s) to users (e.g., subscribers of the carrier) via a network. Acarrier may also refer to a carrier network (e.g., a cellular network)provided and operated by the carrier company. Home carrier network 130may include any cellular network (e.g., a mobile phone network) thatprovides cellular phone service to users (e.g., subscribers) of aparticular carrier (from the perspective of the particular user devices110 a-h). Home carrier network 130 may provide cellular phone servicewithin a particular geographical area (e.g., the United States ofAmerica (USA)). Home carrier network 130 may include a heterogeneousnetwork that includes base stations of different types, including macrobase stations and different types of small cells (not shown in FIG. 1).Home carrier network 130 may have no control over the frequency/volumeof incoming requests for presence information from foreign carriers.Internal presence server 120 may have no control over how many presencerequests are received by internal presence server 120 from user devices110-n-110-x in an external network 170 to a home carrier network 130.

Proxy presence server 140 may perform as a proxy for presenceinformation requests directed to user devices 110 in the home carriernetwork 130 from user devices in external network 170. Proxy presenceserver 140 may be deployed in a mobile carrier network, or into an IPXthat connects mobile carrier networks to act as a cache and proxy forpresence information requests that are directed towards the internalpresence server 120. The IPX may enable traffic between mobile carriernetworks associated with different providers and systems to communicatedata, and voice over internet protocol (VoIP) communications. Proxypresence server 140 may intercept presence requests directed towardsinternal presence server 120 for user devices 110 associated with thehome carrier network 130. In some instances, proxy presence server 140may relay information between external presence servers 150 and internalpresence server 120. In other instances, proxy presence server 140 mayreceive presence requests that may include initial requests and periodicrequests.

Proxy presence server 140 may perform as a proxy that makes a singlequery (for the presence status associated with a particular user device110) to the internal presence server 120 for multiple presence requestsreceived at proxy presence server 140. Proxy presence server 140 maypublish and subscribe to presence information using a variety ofprotocols such as XMPP, SIP or SIMPLE. In some instances, a poorlyconfigured RCS client for a user device 110 may query the home carrier'sinternal presence server 120 for a single subscriber multiple times asecond. Proxy presence server 140 may reduce the workload on internalpresence server 120 and prevent exhausting the capacity of internalpresence server 120. Proxy presence server 140 may interact with devicesand use information from an external network (e.g., an IPX-compliantsystem), such as external presence server 150.

External presence server 150 may be a presence server associated withusers in an external network to home carrier network 130, such asexternal carrier network 170. External presence server 150 may relayrequests for information about the presence or status of user devices110-a to 110-h in home carrier network 130 from user devices 110-n to110-x 1 in external carrier network 170. User devices 110-n to 110-x maysend out a presence request to other subscribing user devices 110associated with an internal presence server 120. External presenceserver 150 may receive a request for presence status from user devices110-n to 110-x in an external carrier network 170 to support particularservices and capabilities. For example, the user device 110 may querywhether a particular person (or particular user device 110) is availablefor a video call, whether the user device 110 is in an LTE network andwhether the requested user device 110 has capability for the particularservices that the requesting user device 110 is requesting with theparticular user device 110.

External carrier network 170 may include a network that is external toand separate from home carrier network 130. For example, externalcarrier network 170 may include a wide area network (WAN), an intranet,a telephone network (e.g., the Public Switched Telephone Network), or acombination of networks. External carrier network 170 may include an IPXthrough which inter-carrier traffic is routinely routed. An IPX maytreat all traffic (e.g., SIP traffic) as pass through traffic withoutdifferentiating between different types of traffic. External carriernetwork 170 may include, for example, an untrusted network, such as theInternet. External carrier network 170 may further include networkdevices such as routers, switches, and/or firewalls.

While FIG. 1 shows a particular number and arrangement of networksand/or devices, in practice, environment 100 may include additionalnetworks/devices, fewer networks/devices, different networks/devices, ordifferently arranged networks/devices than are shown in FIG. 1. Forexample, proxy presence server 140 may be implemented as part of an IPXor an external network.

In implementations described herein, systems may provide a proxypresence service associated with a home carrier network. The proxypresence service may receive requests for presence information fromforeign carriers via an external network and request the presenceinformation from an internal presence server associated with the homecarrier. The proxy presence service may receive subsequent request forpresence information. The proxy presence service may preventinter-carrier communications for presence that may exhaust the capacityof multiple presence platforms in the home carrier network.

FIG. 2 is a diagram of example components of a device 200. Each ofinternal presence server 120, proxy presence server 140 and/or externalpresence server 150, may include one or more devices 200. As shown inFIG. 2, device 200 may include a bus 210, a processor 220, a memory 230,an input device 240, an output device 250, and a communication interface260.

Bus 210 may permit communication among the components of device 200.Processor 220 may include one or more processors or microprocessors thatinterpret and execute instructions. In other implementations, processor220 may be implemented as or include one or more application specificintegrated circuits (ASICs), field programmable gate arrays (FPGAs), orthe like.

Memory 230 may include a random access memory (RAM) or another type ofdynamic storage device that stores information and instructions forexecution by processor 220, a read only memory (ROM) or another type ofstatic storage device that stores static information and instructionsfor the processor 220, and/or some other type of magnetic or opticalrecording medium and its corresponding drive for storing informationand/or instructions.

Input device 240 may include a device that permits an operator to inputinformation to device 200, such as a keyboard, a keypad, a mouse, a pen,a microphone, one or more biometric mechanisms, and the like. Outputdevice 250 may include a device that outputs information to theoperator, such as a display, a speaker, etc.

Communication interface 260 may include a transceiver that enablesdevice 200 to communicate with other devices and/or systems. Forexample, communication interface 260 may include mechanisms forcommunicating with other devices, such as other devices of network 100.

As described herein, device 200 may perform certain operations inresponse to processor 220 executing software instructions contained in acomputer-readable medium, such as memory 230. A computer-readable mediummay be defined as a non-transitory memory device. A memory device mayinclude space within a single physical memory device or spread acrossmultiple physical memory devices. The software instructions may be readinto memory 230 from another computer-readable medium or from anotherdevice via communication interface 260. The software instructionscontained in memory 230 may cause processor 220 to perform processesdescribed herein. Alternatively, hardwired circuitry may be used inplace of or in combination with software instructions to implementprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

Although FIG. 2 shows example components of device 200, in otherimplementations, device 200 may include fewer components, differentcomponents, differently arranged components, or additional componentsthan depicted in FIG. 2. Alternatively, or additionally, one or morecomponents of device 200 may perform one or more other tasks describedas being performed by one or more other components of device 200.

FIG. 3 is a diagram of communications to determine presence via theproxy presence server 120 of FIG. 1. As shown in FIG. 3, communicationsmay include internal presence server 120, proxy presence server 140 andexternal presence server 150.

At step 310, communications may begin when an external user device 110associated with a user (e.g., user X) in an external carrier network 170(not shown in FIG. 3) sends a request for presence informationassociated with another user device 110 in home carrier network 130(e.g., user A). An initial presence status request for user A may berouted through external presence server 150 and directed towardsinternal presence server 120. For example, external user device 110 mayquery whether user A is available and voice enabled. However, thispresence status request may be re-routed and directed to proxy presenceserver 140 by home carrier network 130.

At step 320, proxy presence server 140 may determine that the receivedpresence request is associated with a user device 110 in home carriernetwork 130 for which proxy presence server 140 does not have currentpresence information. Proxy presence server 140 may forward the presencerequest to internal presence server 120. Alternately, proxy presenceserver 140 may format an expanded request for presence information basedon the presence request for user A and send the expanded request tointernal presence server 120. As used herein, an expanded request mayrequest additional information to that originally requested by theexternal user device 110.

At communications step 330, proxy presence server 140 may receive therequested presence information associated with user A from internalpresence server 120. For example, internal presence server 120 maylocate the presentity associated with user A and send a presenceresponse with the requested presence information for user A to proxypresence server 140. Proxy presence server 140 may store the presenceinformation associated with user A in a cache with a configurable TTL.The configurable TTL may be set to a particular time from the initialpresence information is received.

Proxy presence server 140 may send the requested presence informationfor user A to external presence server 150 at step 340. Externalpresence server 150 may forward the requested presence information foruser A to the external user device 110 that requested the information.

At step 350, proxy presence server 140 may receive subsequent requestsfor presence information associated with user A. Proxy presence server140 may receive subsequent request from different external user devices110, which may be associated with the same external presence server 150or different external presence servers 150.

Proxy presence server 140 may determine whether the requested presenceinformation is stored in an associated cache. If so, proxy presenceserver 140 may determine whether the request has been received withinthe configurable TTL associated with the cached presence information. Ininstances in which the request has been received within the configurableTTL, proxy presence server 140 may send a presence response regardinguser A to external presence server 150 based on the cached presenceinformation, which may forward the presence status of user A to therequesting external user device 110.

FIG. 4 is a block diagram of exemplary functional or logical componentsof proxy presence server 140 (e.g., stored in memory 230 of proxypresence server 140). Proxy presence server 140 may include externalinterface module 410, cache module 420, query module 430 and a presencedatabase 440. The configuration of components of proxy presence server140 illustrated in FIG. 4 is for illustrative purposes. Proxy presenceserver 140 may include additional, fewer and/or different componentsthan those depicted in FIG. 4.

External interface module 410 may function as an external interface forpresence information to foreign carriers or IPX providers for example asdescribed below with respect to FIG. 5. External interface module 410may receive queries for presence information.

Cache module 420 may cache presence information for subscribers it hasrecently received queries for a set amount of time, such as describedbelow with respect to FIG. 6. Cache module 420 may cache each presenceentry associated with user devices 110 within the home carrier network130 with a TTL in presence database 440.

Query module 430 may receive queries from foreign networks (e.g.,external network 170) for the capabilities of a subscriber. Query module430 may determine a response to the query based on whether the presenceinformation is cached in presence database 440, such as described belowwith respect to FIG. 7. Query module 430 may serve the presenceinformation and offload that demand from the internal presence server120.

The configuration of components of proxy presence server 140 illustratedin FIG. 4 is for illustrative purposes. Other configurations may beimplemented. Proxy presence server 140 may include additional, fewerand/or different components than those depicted in FIG. 4.

FIG. 5 is an exemplary functional block diagram of external interfacemodule 410. As shown in FIG. 5, external interface module 410 mayinclude presence request logic 510 and presence response logic 520.

Presence request logic 510 may receive communications from externalpresence servers 150 requesting presence information for user devices110 in the home carrier network 130. Presence request logic 510 mayforward the request to query module 430.

Presence response logic 520 may identify a requesting external presenceserver 150. Presence response logic 520 may provide a response to thepresence status request to the identified external presence server 150.In some instances, presence response logic 520 may identify externalpresence servers 150 that request presence information above apredetermined threshold number of times within a time window (e.g.,based on a poorly configured RCS client) and take appropriate actionand/or provide an appropriate response to the external presence server150.

FIG. 6 is an exemplary functional block diagram of cache module 420. Asshown in FIG. 6, cache module 420 may include presentity logic 610 andTTL logic 620.

Presentity logic 610 may cache presence information for subscribers ithas recently received queries for a set amount of time. Presentity logic610 may assume responsibility for handling queries and allow theinternal presence server to offload the demand for these queries fromthe home network served presence platform. Internal presence server 120may focus available resources on serving subscribers within the homenetwork. Presentity logic 610 may retrieve capabilities data for everysubscriber on a configurable interval from internal presence server 120.

TTL logic 620 may provide a TTL and monitor each presentity based on theTTL. A presentity may include an entity that has presence informationassociated with it, such as status, reachability, etc. TTL logic 620 mayreceive instructions to configure the TTL from an administratorassociated with the home carrier network 130. Presentity logic 610 mayretrieve data once for all foreign carriers within the configurable TTL.TTL logic 620 may thereby prevent multiple retrievals by individualhandsets (i.e., external user devices 110).

FIG. 7 is an exemplary functional block diagram of query module 430. Asshown in FIG. 7, query module 430 may include query service logic 710and query update logic 720.

Query service logic 710 may receive queries from external network 170for the capabilities of a subscriber. Query service logic 710 may servethe presence information and offload that demand from the internalpresence server 120. Query service logic 710 may access the cachedpresence information for that subscriber using a configurable TTL. Ifanother query is received for that subscriber, query service logic 710may serve the query directly, with no impact to the internal presenceserver 120.

Query update logic 720 may update presence information. In instances inwhich query module 430 is queried or notified of a subscribe (to thepresence information for a user device 110) by a device outside of thehome carrier network 130, query update logic 720 may query the internalpresence server 120 and respond to the query.

FIG. 8 is a flowchart of an exemplary process 800 for providing a proxypresence service for a user device associated with a home carriernetwork. Process 800 may execute in proxy presence server 140. Inanother implementation, some or all of process 800 may be performed byanother device or group of devices, including or excluding proxypresence server 140. It should be apparent that the process discussedbelow with respect to FIG. 8 represents a generalized illustration andthat blocks/steps may be added or existing blocks/steps may be removed,modified or rearranged without departing from the scope of process 800.

At block 802, proxy presence server 140 may receive a presence statusrequest for a user device 110 of home carrier network 130 from externalpresence server 150. The presence status request may include a requestfor information on multiple different types of presence based features.For example, the presence information may include RCS chat capabilityinformation. Additionally, the query may include whether the user device110 is voice enabled and whether the user device 110 is in a networkthat supports enhanced services.

At block 804, proxy presence server 140 may send a presence statusrequest to internal presence server 120. For example, proxy presenceserver 140 may identify a uniform resource locator (URL) associated withinternal presence server 120 and forward the presence status request viathe URL.

Proxy presence server 140 may receive the presence status of the userfrom internal presence server 120 (block 806). For example, internalpresence server 120 may query the user device 110 regarding therequested presence information. Internal presence server 120 may sendthe current presence information to proxy presence server 140.

Proxy presence server 140 may store the presence information with aconfigurable TTL in an associated database (block 808). For example,proxy presence server 140 may store the presence information indexedwith an identifier for user device 110 and other information associatedwith user device 110 (e.g., a network address, etc.). The presenceinformation may includes whether a subscriber plan associated with theuser device 110 covers the communication (i.e., the communication is ofa type for which charges and other information are defined and recordedby the subscriber plan).

Proxy presence server 140 may send the presence status of the user tothe requesting external presence server 140 (block 810). Proxy presenceserver 140 may send presence information requested by the external userdevice 110.

Proxy presence server 140 may receive subsequent requests for presencestatus of the user within the TTL (block 812). For example, another userdevice 110 (or the same external user device 110) may send a requestthrough another external presence server 140 (or the same externalpresence server 140) for the presence status of the same user within thetime window of the TTL. Proxy presence server 140 may determine whethera stored entry associated with the user for the presence status exists,and send a presence status request to the internal presence server 120in response to a determination that a stored entry associated with theuser device for the presence status does not exist. In instances inwhich presence RCS services are deployed, world wide mobile operatorsmay have minimal or no insight into the number of foreign carriersubscribers that will populate the address books of home carriersubscribers. Proxy presence server 140 may allow the internal presenceserver 120 to allocate resources to providing presence status responsesto home carrier subscribers.

Proxy presence server 140 may send the presence status of the user toall requesting external presence servers 140 within the TTL (block 814).Proxy presence server 140 may send the presence status response throughanother external presence server 140 (or the same external presenceserver 140) within the time window of the TTL.

Systems and/or methods described herein may receive requests forpresence information from foreign carriers via an external network andrequest the presence information from an internal presence serverassociated with a home carrier. The systems may cache the presenceinformation for a particular subscriber using a configurable TTL. Thesystems may receive subsequent requests for presence information andprovide presence status response based on the stored presenceinformation.

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense. For example, while seriesof blocks have been described with respect to FIG. 8, the order of theblocks may be modified in other implementations. Further, non-dependentblocks may be performed in parallel.

It will be apparent that systems and/or methods, as described above, maybe implemented in many different forms of software, firmware, andhardware in the implementations illustrated in the figures. The actualsoftware code or specialized control hardware used to implement thesesystems and methods is not limiting of the embodiments. Thus, theoperation and behavior of the systems and methods were described withoutreference to the specific software code—it being understood thatsoftware and control hardware can be designed to implement the systemsand methods based on the description herein.

Further, certain portions of the invention may be implemented as a“component” or “system” that performs one or more functions. Thesecomponents/systems may include hardware, such as a processor, an ASIC,or a FPGA, or a combination of hardware and software.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the embodiments unlessexplicitly described as such. Also, as used herein, the articles “a”,“an” and “the” are intended to include one or more items. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A computer-implemented method comprising:receiving, from an external presence server at a proxy presence device,a presence status request from a rich communication service(RCS)-enabled client device for first presence information associatedwith a user device in a home carrier network; determining, by the proxypresence device, that the first presence information is not stored in anassociated database; generating, by the proxy presence device and basedon the determining, an expanded presence status request requesting thefirst presence information and second presence information associatedwith the user device with respect to the home carrier network; sendingthe expanded presence status request to an internal presence server inthe home carrier network; receiving an expanded presence status of theuser device, wherein the expanded presence status includes the firstpresence information and the second presence information; storing theexpanded presence status of the user device with a time to live (TTL) inthe associated database; sending the first presence information to theexternal presence server; receiving multiple subsequent requests fromthe RCS-enabled client device for a presence status of the user devicewithin a time window of the TTL; identifying, based on the multiplesubsequent requests exceeding a threshold number of requests within thetime window, the RCS-enabled client device as being improperlyconfigured; and notifying the external presence server that theRCS-enabled client device is improperly configured.
 2. Thecomputer-implemented method of claim 1, wherein receiving the presencestatus request further comprises: receiving a request for richcommunication services.
 3. The computer-implemented method of claim 1,wherein receiving the presence status request further comprises:receiving a query whether the user device is voice enabled.
 4. Thecomputer-implemented method of claim 1, wherein receiving the presencestatus request further comprises: receiving a query whether the homecarrier network network supports enhanced services.
 5. Thecomputer-implemented method of claim 1, further comprising: receiving atleast one request from a different external presence server than theexternal presence server.
 6. The computer-implemented method of claim 1,further comprising: retrieving capabilities data for the user device ona configurable interval.
 7. The computer-implemented method of claim 1,wherein the proxy presence device is configured to use ExtensibleMessaging and Presence Protocol (XMPP) to publish and subscribe to thefirst presence information and the second presence information.
 8. Thecomputer-implemented method of claim 1, wherein the first presenceinformation includes whether a subscriber plan associated with the userdevice covers RCS.
 9. The computer-implemented method of claim 8,wherein the second presence information is associated with a videoportion of a voice over long term evolution (VOLTE) call.
 10. Thecomputer-implemented method of claim 8, wherein the second presenceinformation includes whether the user device includes a camera.
 11. Thecomputer-implemented method of claim 1, wherein sending the expandedpresence request comprises: determining a uniform resource locator (URL)associated with the internal presence server; and sending the expandedpresence status request to the internal presence server via the URL. 12.A device, comprising: a communication interface; a memory to store aplurality of instructions; and a processor configured to execute theinstructions in the memory to: receive, via the communication interfacefrom an external presence server, a presence status request from a richcommunication service (RCS)-enabled client device for first presenceinformation associated with a user device in a home carrier network;determine that the first presence information is not stored in anassociated database; generate, based on the determination, an expandedpresence status request requesting the first presence information andsecond presence information associated with the user device with respectto the home carrier network; send, via the communication interface, theexpanded presence status request to an internal presence server in thehome carrier network; receive, via the communication interface, anexpanded presence status of the user device, wherein the expandedpresence status includes the first presence information and the secondpresence information; store the expanded presence status of the userdevice with a time to live (TTL) in the associated database; send, viathe communication interface, the first presence information to theexternal presence server; receive, via the communication interface,multiple subsequent requests from the RCS-enabled client device for apresence status of the user device within a time window of the TTL;identify, based on the multiple subsequent requests exceeding athreshold number of requests within the time window, the RCS-enabledclient device as being improperly configured; and notify, via thecommunication interface, the external presence server that theRCS-enabled client device is improperly configured.
 13. The device ofclaim 12, wherein, when receiving the presence status request, theprocessor is further to: receive a request for rich communicationservices.
 14. The device of claim 12, wherein when receiving thepresence status request, the processor is further to: receive a querywhether the user device is voice enabled.
 15. The device of claim 12,wherein when receiving the presence status request, the processor isfurther to: receive a query whether the home carrier network supportsenhanced services.
 16. The device of claim 12, wherein the processor isfurther to: receive at least one request from a different externalpresence server than the external presence server.
 17. The device ofclaim 12, wherein the device is configured to use Extensible Messagingand Presence Protocol (XMPP) to publish and subscribe to the firstpresence information and the second presence information.
 18. Anon-transitory computer-readable medium including instructions to beexecuted by a processor, the instructions including one or moreinstructions, when executed by the processor, for causing the processorto: receive, from an external presence server, a presence status requestfrom a rich communication service (RCS)-enabled client device for firstpresence information associated with a user device in a home carriernetwork; determine that the first presence information is not stored inan associated database; generate, based on the determination, anexpanded presence status request requesting the first presenceinformation and second presence information associated with the userdevice with respect to the home carrier network; send the expandedpresence status request to an internal presence server in the homecarrier network, wherein the expanded presence status includes the firstpresence information and the second presence status information; receivean expanded presence status of the user device; store the expandedpresence status of the user device with a time to live (TTL) in theassociated database; send the first presence information to the externalpresence server; receive multiple subsequent requests for a presencestatus of the user device within a time window of the TTL; identify,based on the multiple subsequent requests exceeding a threshold numberof requests within the time window, the RCS-enabled client device asbeing improperly configured; and notify the external presence serverthat the RCS-enabled client device is improperly configured.
 19. Thenon-transitory computer-readable medium of claim 18, wherein, whenreceiving the presence status request, the one or more instructionsfurther includes instructions for causing the processor to: receive arequest for rich communication services.
 20. The non-transitorycomputer-readable medium of claim 18, wherein, when receiving thepresence status request, the one or more instructions further includesinstructions for causing the processor to: receive a query whether theuser device is voice enabled.